Providing procedures

ABSTRACT

For providing procedures, a synchronization module stores a plurality of equipment procedures in a procedure database. Each equipment procedure corresponds to an equipment instance of a plurality of equipment instances and each equipment instance corresponds to an equipment reference code. The synchronization module further synchronizes the plurality of equipment procedures to a mobile device. A retrieval module receives a first equipment reference code at the mobile device and retrieves a first equipment procedure indexed to the first equipment reference code.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation-in-part application of and claims priority toU.S. Pat. No. 8,751,504 (application Ser. No. 13/653,187) entitled“PROVIDING PROCEDURES” and filed on Oct. 16, 2012 for Jimi Michalscheck,which is incorporated herein in its entirety by reference, and is acontinuation-in-part of and claims priority to U.S. patent applicationSer. No. 14/271,257 entitled “PROVIDING EQUIPMENT PERMITS AND CONFINEDSPACE ACCESS PROCEDURES” and filed on May 6, 2014 for Jimi Michalscheck,which is incorporated herein in its entirety by reference.

FIELD

The subject matter disclosed herein relates to procedures and moreparticularly relates to providing procedures.

BACKGROUND Description of the Related Art

Equipment, particularly industrial equipment, can be dangerous tomaintain and operate. Operational safety is enhanced when appropriateprocedures are readily accessible.

BRIEF SUMMARY

A method for providing procedures is disclosed. A synchronization modulestores a plurality of equipment procedures in a procedure database. Eachequipment procedure corresponds to an equipment instance of a pluralityof equipment instances and each equipment instance corresponds to anequipment reference code. The synchronization module furthersynchronizes the plurality of equipment procedures to a mobile device. Aretrieval module receives a first equipment reference code at the mobiledevice and retrieves a first equipment procedure indexed to the firstequipment reference code. A program product and an apparatus alsoperform the functions of the method.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the embodiments of the invention will bereadily understood, a more particular description of the embodimentsbriefly described above will be rendered by reference to specificembodiments that are illustrated in the appended drawings. Understandingthat these drawings depict only some embodiments and are not thereforeto be considered to be limiting of scope, the embodiments will bedescribed and explained with additional specificity and detail throughthe use of the accompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of asystem for providing procedures;

FIG. 2A is a schematic block diagram illustrating one embodiment of aprocedure database;

FIG. 2B is a schematic block diagram illustrating one embodiment ofprocedure data;

FIG. 2C is a schematic block diagram illustrating one embodiment ofequipment data;

FIG. 2D is a schematic block diagram illustrating one embodiment of anequipment status;

FIG. 2E is a schematic block diagram illustrating one embodiment of auser database 140;

FIG. 2F is a schematic block diagram illustrating one embodiment of anaudit database 165;

FIG. 2G is a schematic block diagram illustrating one embodiment of anaudit report;

FIG. 2H is a schematic block diagram illustrating one embodiment of asite list;

FIG. 2I is a schematic block diagram illustrating one alternateembodiment of the site list;

FIG. 2J is a schematic block diagram illustrating one embodiment of atutorial database;

FIG. 3A is a schematic block diagram illustrating one embodiment of acomputer;

FIG. 3B is a schematic block diagram illustrating one embodiment of aprocedure apparatus;

FIG. 4A is a schematic flow chart diagram illustrating one embodiment ofa procedure provision method;

FIG. 4B is a schematic flow chart diagram illustrating one embodiment ofan update method;

FIG. 4C is a schematic flow chart diagram illustrating one embodiment ofa status provision method;

FIG. 4D is a schematic flow chart diagram illustrating one embodiment ofan audit method; and

FIG. 4E is a schematic flow chart diagram illustrating one embodiment ofa tutorial provision method.

DETAILED DESCRIPTION

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusiveand/or mutually inclusive, unless expressly specified otherwise. Theterms “a,” “an,” and “the” also refer to “one or more” unless expresslyspecified otherwise.

Furthermore, the described features, advantages, and characteristics ofthe embodiments may be combined in any suitable manner. One skilled inthe relevant art will recognize that the embodiments may be practicedwithout one or more of the specific features or advantages of aparticular embodiment. In other instances, additional features andadvantages may be recognized in certain embodiments that may not bepresent in all embodiments.

These features and advantages of the embodiments will become more fullyapparent from the following description and appended claims, or may belearned by the practice of embodiments as set forth hereinafter. As willbe appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method, and/or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module,” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having program code embodied thereon.

Many of the functional units described in this specification have beenlabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom VLSI circuits or gate arrays,off-the-shelf semiconductors such as logic chips, transistors, or otherdiscrete components. A module may also be implemented in programmablehardware devices such as field programmable gate arrays, programmablearray logic, programmable logic devices or the like.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of program code may, forinstance, comprise one or more physical or logical blocks of computerinstructions which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together, but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of program code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.Where a module or portions of a module are implemented in software, theprogram code may be stored and/or propagated on in one or more computerreadable medium(s).

The computer readable medium may be a tangible and/or non-transitorycomputer readable storage medium storing the program code. The computerreadable storage medium may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples of the computer readable storage medium mayinclude but are not limited to a portable computer diskette, a harddisk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), aportable compact disc read-only memory (CD-ROM), a digital versatiledisc (DVD), an optical storage device, a magnetic storage device, aholographic storage medium, a micromechanical storage device, or anysuitable combination of the foregoing. In the context of this document,a computer readable storage medium may be any tangible medium that cancontain, and/or store program code for use by and/or in connection withan instruction execution system, apparatus, or device.

In one embodiment, the computer readable medium may comprise acombination of one or more computer readable storage mediums and one ormore computer readable signal mediums. For example, program code may beboth propagated as an electromagnetic signal through a fiber optic cablefor execution by a processor and stored on RAM storage device forexecution by the processor.

Program code for carrying out operations for aspects of the presentinvention may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++, PHP or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

The computer program product may be shared, simultaneously servingmultiple customers in a flexible, automated fashion. The computerprogram product may be standardized, requiring little customization andscalable, providing capacity on demand in a pay-as-you-go model.

The computer program product may be stored on a shared file systemaccessible from one or more servers. The computer program product may beexecuted via transactions that contain data and server processingrequests that use Central Processor Unit (CPU) units on the accessedserver. CPU units may be units of time such as minutes, seconds, hourson the central processor of the server. Additionally the accessed servermay make requests of other servers that require CPU units. CPU units arean example that represents but one measurement of use. Othermeasurements of use include but are not limited to network bandwidth,memory usage, storage usage, packet transfers, complete transactionsetc.

When multiple customers use the same computer program product via sharedexecution, transactions are differentiated by the parameters included inthe transactions that identify the unique customer and the type ofservice for that customer. All of the CPU units and other measurementsof use that are used for the services for each customer are recorded.When the number of transactions to any one server reaches a number thatbegins to affect the performance of that server, other servers areaccessed to increase the capacity and to share the workload. Likewisewhen other measurements of use such as network bandwidth, memory usage,storage usage, etc. approach a capacity so as to affect performance,additional network bandwidth, memory usage, storage etc. are added toshare the workload.

The measurements of use used for each service and customer are sent to acollecting server that sums the measurements of use for each customerfor each service that was processed anywhere in the network of serversthat provide the shared execution of the computer program product. Thesummed measurements of use units are periodically multiplied by unitcosts and the resulting total computer program product service costs arealternatively sent to the customer and or indicated on a web siteaccessed by the customer which then remits payment to the serviceprovider.

In one embodiment, the service provider requests payment directly from acustomer account at a banking or financial institution. In anotherembodiment, if the service provider is also a customer of the customerthat uses the computer program product, the payment owed to the serviceprovider is reconciled to the payment owed by the service provider tominimize the transfer of payments.

The computer program product may be integrated into a client, server andnetwork environment by providing for the computer program product tocoexist with applications, operating systems and network operatingsystems software and then installing the computer program product on theclients and servers in the environment where the computer programproduct will function.

In one embodiment software is identified on the clients and serversincluding the network operating system where the computer programproduct will be deployed that are required by the computer programproduct or that work in conjunction with the computer program product.This includes the network operating system that is software thatenhances a basic operating system by adding networking features.

In one embodiment, software applications and version numbers areidentified and compared to the list of software applications and versionnumbers that have been tested to work with the computer program product.Those software applications that are missing or that do not match thecorrect version will be upgraded with the correct version numbers.Program instructions that pass parameters from the computer programproduct to the software applications will be checked to ensure theparameter lists match the parameter lists required by the computerprogram product. Conversely parameters passed by the softwareapplications to the computer program product will be checked to ensurethe parameters match the parameters required by the computer programproduct. The client and server operating systems including the networkoperating systems will be identified and compared to the list ofoperating systems, version numbers and network software that have beentested to work with the computer program product. Those operatingsystems, version numbers and network software that do not match the listof tested operating systems and version numbers will be upgraded on theclients and servers to the required level.

In response to determining that the software where the computer programproduct is to be deployed, is at the correct version level that has beentested to work with the computer program product, the integration iscompleted by installing the computer program product on the clients andservers.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and computer program products according toembodiments of the invention. It will be understood that each block ofthe schematic flowchart diagrams and/or schematic block diagrams, andcombinations of blocks in the schematic flowchart diagrams and/orschematic block diagrams, can be implemented by program code. Theprogram code may be provided to a processor of a general purposecomputer, special purpose computer, sequencer, or other programmabledata processing apparatus to produce a machine, such that theinstructions, which execute via the processor of the computer or otherprogrammable data processing apparatus, create means for implementingthe functions/acts specified in the schematic flowchart diagrams and/orschematic block diagrams block or blocks.

The program code may also be stored in a computer readable medium thatcan direct a computer, other programmable data processing apparatus, orother devices to function in a particular manner, such that theinstructions stored in the computer readable medium produce an articleof manufacture including instructions which implement the function/actspecified in the schematic flowchart diagrams and/or schematic blockdiagrams block or blocks.

The program code may also be loaded onto a computer, other programmabledata processing apparatus, or other devices to cause a series ofoperational steps to be performed on the computer, other programmableapparatus or other devices to produce a computer implemented processsuch that the program code which executed on the computer or otherprogrammable apparatus provide processes for implementing thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and computerprogram products according to various embodiments of the presentinvention. In this regard, each block in the schematic flowchartdiagrams and/or schematic block diagrams may represent a module,segment, or portion of code, which comprises one or more executableinstructions of the program code for implementing the specified logicalfunction(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and program code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 is a schematic block diagram illustrating one embodiment of asystem 100 for providing procedures. The system 100 provides a procedurefor equipment 160. The system 100 includes a server 120, a proceduredatabase 125, a user database 140, an audit database 165, a tutorialdatabase 170, a workstation 135, a network 115, a mobile device 105, aplurality of equipment 160, and an equipment reference code 205 for eachequipment instance 160. For simplicity, a single equipment instance 160and a single equipment reference code 205 are shown.

The equipment 160 may be electrical equipment, hydraulic equipment,compressed air equipment, steam equipment, mechanical tools, protectiveequipment, refrigeration equipment, power lines, hydraulic lines, steamlines, or combinations thereof. Alternatively, the equipment 160 may becontainers of hazardous substances, containers of biological substances,containers of chemical substances, or combinations thereof.

An equipment procedure is often specified for safely operating and/ormaintaining the equipment 160. The equipment procedure may specify inmore detail the process steps, tools, safety equipment, and the likethat must be complied with when operating and maintaining the equipment160. The equipment 160 may also require one or more equipment permits tocomply with regulations for the equipment 160.

Unfortunately, in the past the equipment procedures and/or equipmentpermits have not always been available when there is a need to operateand/or maintain the equipment 160. For example, when equipmentprocedures are centrally stored, a user may need to anticipate andacquire the required equipment procedures before operating and/ormaintaining the equipment 160.

In addition, the user that had earlier acquired the equipment proceduremay be unaware that the equipment procedure had been updated. As aresult, in the past, users have often lacked the latest equipmentprocedures or did not have the latest equipment permits.

The embodiments described herein provide the most current equipmentprocedures to the user as will be described hereafter. In addition, theembodiments provide current equipment permits. As a result, even whenworking remotely, the user is assured of having the most currentequipment procedures and/or equipment permits, allowing the user tosafely operate or maintain the equipment 160.

In order to enhance safety and comply with safety regulations, theavailability and proper use of an equipment procedure for the equipment160 may be periodically audited. Such an audit may be difficult totrack, manage, and report. The embodiments also record if the userfollows an equipment procedure and/or complies with an equipment permitto an audit report and synchronizes the audit report to the auditdatabase 165 as will be described hereafter.

A user may be uncertain as to how to apply equipment procedures. Theembodiments also provide equipment tutorials associated with theequipment 160. The user may access the equipment tutorials to learn howto properly carry out steps of the equipment procedures as will bedescribed hereafter.

The equipment reference code 205 is associated with the equipment 160.The equipment reference code 205 may be affixed to the equipment 160.Alternatively, the equipment reference code may be mounted near theequipment 160. In one embodiment, the equipment reference code 205 isprinted on an adhesive label that is affixed to the equipment 160. Theequipment reference code 205 may be encoded as a Quick Reference (QR)code. In addition, the equipment reference code 205 may also bedisplayed in a human readable form.

In an alternate embodiment, the equipment reference code 205 is encodedas a barcode. The equipment reference code 205 may also be encoded as anidentification code broadcast via a Radio Frequency Identifier (RFID).

The equipment reference code 205 refers to equipment procedures storedin the procedure database 125. In addition, the equipment reference code205 may refer to equipment permits for the equipment 160. In oneembodiment, the equipment reference code 205 is used as an index to theequipment procedures and/or equipment permits. The equipment proceduresand equipment permits may be created, edited, updated, and/or deletedfrom the workstation 135.

The server 120 may communicate the equipment procedures and/or equipmentpermits through the network 115 to the mobile device 105. The network115 maybe the Internet, a mobile telephone network, a wide area network,a local area network, a wireless network, or combinations thereof.

The server 120 may synchronize all the equipment procedures and/orequipment permits in the procedure database 125 to the mobile device 105so that the mobile device 105 stores a copy of all the equipmentprocedures and/or equipment permits in the procedure database 125. Thusall the equipment procedures and/or equipment permits may be availableon the mobile device 105. In addition, the server 120 may synchronizeequipment tutorials from the tutorial database 170 to the mobile device105.

The equipment procedures may be grouped by site. In one embodiment, theserver 120 maintains a site list of all the equipment 160 at a specifiedsite. The site list may include an equipment reference code 205 for eachequipment instance 160 at the specified site. Alternatively, the sitelist may include a procedure identifier for each equipment instance 160at the specified site. The server 120 may synchronize only the equipmentprocedures and/or equipment permits of a site list to the mobile device105 in response to receiving an equipment reference code 205 and/orprocedure identifier for one of the equipment instances 160 on the sitelist. In one embodiment, the equipment procedures and/or equipmentpermits are organized as a database, a data structure, or combinationsthereof on the mobile device 105.

The mobile device 205 may be a tablet computer, a mobile phone, anotebook computer, a personal digital assistant, or the like. The mobiledevice 105 may receive 145 the equipment reference code 205. In oneembodiment, the mobile device 105 optically scans a QR code encoding theequipment reference code 205. Alternatively, the mobile device 105 mayoptically scan a barcode encoding the equipment reference code 205. In acertain embodiment, the mobile device 105 wirelessly queries an RFIDequipment reference code 205 and receives the equipment reference code205 encoded in a wireless response from the RFID.

The mobile device 105 may use the equipment reference code 205 as anindex to retrieve the equipment procedures and/or equipment permitsassociated with the equipment reference code 205 from the mobile device105. The mobile device 105 may display the equipment permits and anyinformation associated with the equipment permits. The mobile device 105may also display the equipment procedure, allowing the user to performthe equipment procedure on the equipment 160.

If the equipment procedures and/or equipment permits associated with theequipment reference code 205 are not stored on the mobile device 105,the mobile device 105 may use the equipment reference code 205 torequest equipment procedures and/or equipment permits from the server120 through the network 115. The server 120 may synchronize theequipment procedures and/or equipment permits from the proceduredatabase 125 through the network 115 to the mobile device 105 so thatthe equipment procedures and/or equipment permits may be displayed bythe mobile device 105.

By synchronizing the equipment procedures and/or equipment permits tothe mobile device 105, a user may reference the correct equipment permitfor the equipment 160 even if a physical copy of the equipment permit isnot available locally. In addition, the user may access the correctequipment procedure for the equipment 160 on the mobile device 105 evenif a paper document with the equipment procedure has been removed fromthe equipment 160 or if an incorrect equipment procedure is placed withthe equipment 160.

FIG. 2A is a schematic block diagram illustrating one embodiment of aprocedure database 125. The procedure database 125 is the proceduredatabase 125 of FIG. 1. The procedure database 125 includes proceduredata 210 and equipment data 211 as will be described hereafter. Theprocedure database 125 may include a plurality of tables, with aplurality of entries in each table. In addition, the procedure data 210and equipment data 211 may be associated with one or more audit reports230. In one embodiment, the audit reports 230 are stored in the auditdatabase 165 as will be described hereafter.

FIG. 2B is a schematic block diagram illustrating one embodiment ofprocedure data 210. The procedure data 210 is the procedure data 210 ofFIG. 2A. The procedure data 210 may include a procedure identifier 225,an equipment procedure 215, a procedure status 217, a procedure changehistory 220, and a tutorial identifier 296.

The procedure identifier 225 may uniquely identify the equipmentprocedure 215. The procedure identifier 225 may be an index to theprocedure database 125. In addition, the procedure identifier 225 mayinclude a title.

The equipment procedure 215 may include instructions in text, hypertext,audio, video, images, and combinations thereof. The equipment procedure215 may be displayed and/or transmitted to allow the user to perform oneor more operations on the equipment 160. For example, the equipmentprocedure 215 may specify safety equipment for use with equipment 160,may specify safety checks for operating the equipment 160, may specifyoperations for maintaining the equipment 160, and may specify actions tobe performed while operating the equipment 160. In a certain embodiment,the equipment procedure 215 includes a contact link that connects theuser to an expert or service personnel.

The equipment procedure 215 may be an arc flash procedure. The arc flashprocedure may specify personal protective equipment, voltage andamperage magnitudes, energy source locations, energy dissipationprocedures, and the like for the machine 160. In addition, the arc flashprocedure may specify audit requirements including audit results andaudit frequencies.

In one embodiment, the equipment procedure 215 is a machine guardingprocedure. The machine guarding procedure may specify guards for themachine 160. In addition, the machine guarding procedure may specify theplacement of the guards relative to the machine 160. In one embodiment,the machine guarding procedure may specify how to test the guards. Inaddition, the machine guarding procedure may specify how to maintain theguards. In one embodiment, the machine guarding procedure may specifyaudit requirements including audit results and audit frequencies.

The equipment procedure 215 may also be a maintenance procedure. In oneembodiment, the maintenance procedure is a preventive maintenanceprocedure. The maintenance procedure may specify how to maintain theequipment 160. In one embodiment, the maintenance procedure may only beaccessed after accessing and/or completing a lockout procedure. Themaintenance procedure may also specify audit requirements includingaudit results and audit frequencies.

The equipment procedure 215 may further be an operating procedure. Theoperating procedure may specify how to operate the equipment 160. Theoperating procedure may specify personal protective equipment foroperating the equipment 160, the placement of the equipment 160, safetydevices for the equipment 160, testing of the equipment 160, processsteps for using equipment 160, and the like. In one embodiment, theoperating procedure specifies audit requirements including audit resultsand audit frequencies.

In one embodiment, the equipment procedure 215 is an equipment hazardprocedure. The equipment hazard procedure may show known hazards for theequipment 160. In one embodiment, the equipment hazard procedure may belinks to related equipment procedures 215. In one embodiment, theequipment hazard procedure may list the hazards by frequency.Alternatively, the equipment hazard procedure may list the hazards byoperation type. In one embodiment, the equipment hazard procedurespecifies audit requirements including audit results and auditfrequencies.

The equipment status 217 may indicate that an audit for the equipment160 and/or the equipment procedure 215 is passed, failed, and/or thatthe audit is complete. The procedure change history 220 may recordchanges to the equipment procedure 215. In one embodiment, changes arerecorded to the procedure change history 220 automatically when thechanges are made. For example, the user may be prompted to enter adescription of the change after entering the change. Alternatively, thechanges may be recorded from comparisons of different versions of theequipment procedure 215. The tutorial identifier 296 identifies one ormore equipment tutorials associated with the equipment procedure 215.

FIG. 2C is a schematic block diagram illustrating one embodiment of theequipment data 211. The equipment data 211 is the equipment data 211 ofFIG. 2A. The procedure data 210 may include the equipment reference code205, the equipment permit 270, a permit change history 275, one or moreequipment statuses 280, one or more procedure identifiers 225, and atutorial identifier 296. The equipment reference code 205 may index theequipment data 211 in the procedure database 125. In addition, theequipment reference code 205 may identify the equipment 160.

The equipment permit 270 may be issued by regulatory body. The equipmentpermit 270 may specify operational and/or maintenance requirements forthe equipment 160, requirements for a user of the equipment 160, safetyrequirements for equipment 160, environmental the equipment 160,reporting requirements for the equipment 160, and test procedures forthe equipment 160.

The permit change history 275 may record changes to the equipment permit270. The changes to the equipment permit 270 may be recordedautomatically when the changes are made, such as by prompting for adescription of the changes in response to a change entry. In oneembodiment, the changes to the equipment permit 270 are manually enteredfrom the workstation 135. In addition, the changes may be determinedfrom a comparison of different versions of the equipment permit 270.

The equipment status 280 may record specific status information aboutthe equipment 160. The equipment status 280 is described in more detailhereafter in FIG. 2D. One or more procedure identifiers 225 may identifyequipment procedures 215 for the equipment 160. The tutorial identifier296 identifies one or more equipment tutorials associated with theequipment 160 of the equipment data 211.

FIG. 2D is a schematic block diagram illustrating one embodiment of anequipment status 280. The equipment status 280 is the equipment status280 of FIG. 2C. In the depicted embodiment, the equipment status 280includes an operations log 290 and a maintenance log 292. The operationslog 290 may record events during operation of the equipment 160. Themaintenance log 292 may record maintenance performed for the equipment160.

FIG. 2E is a schematic block diagram illustrating one embodiment of auser database 140. The user database 140 is the user database 140 ofFIG. 1. The user database 140 maybe organized as a plurality of tables.The user database 140 includes user data 260. The user data 260 mayinclude a user name, a user identifier such as employee number, a userimage, a biometric identifier, a signature, and the like. In oneembodiment, one or more audit reports 230 are associated with the userdata 260.

FIG. 2F is a schematic block diagram illustrating one embodiment of anaudit database 165. The audit database 165 is the audit database 165 ofFIG. 1. The audit database 165 may store a plurality of audit reports230 as will be described hereafter in FIG. 2F.

FIG. 2G is a schematic block diagram illustrating one embodiment of anaudit report 230. The audit report 230 is the audit report 230 of FIGS.2A, 2E, and 2F. The audit report 230 may be embodied in one or moretables, a data structure, and the like. The audit report 230 includesauditor data 232, an audit time 234, audit results 236, the useridentifier 238, an audit frequency 237, an attestation 240, an auditstatus 242, the equipment reference code 205, the procedure identifier225, and/or audit issues 243.

The auditor data 232 may identify an auditor performing the audit. Inone embodiment, the auditor is identified as the user logging into themobile device 105 to perform the audit. In one embodiment, the auditormay login to the mobile device 105 and select an audit option. Anidentifier for the auditor may be stored with the auditor data 232. Theaudit time 234 may be a timestamp indicating when the audit was startedand/or completed.

The audit result 236 may describe the results of the audit. The auditresults 236 may include a data structure encoding results of the audit,hypertext encoding results of the audit, a written description ofresults of the audit, a verbal description of results of the audit, anda video description of results of the audit, and combinations thereof.Elements of the audit results 236 may correspond to steps of anequipment process 215. In addition, elements of the audit results 236may correspond to requirements of the equipment permit 270. The auditstatus 242 may summarize the audit such as with a “pass” or “fail”indication. Alternatively, the audit status 242 may summarize the auditsuch as with an “in process” indication.

In one embodiment, the user identifier 238 identifies the userperforming operations and/or maintenance with the equipment 160. Theuser identifier 238 may refer to the user data 260.

The audit frequency 237 may specify a frequency for performing theaudit. For example, the audit frequency 237 may specify that the auditbe performed after a specified time interval such as every six months.Alternatively, the audit frequency 237 may specify that the audit beperformed after a specified number of equipment procedures 215, such asafter 10 equipment procedures 215.

The equipment reference code 205 is the equipment reference code 205 ofFIG. 1. The procedure identifier 225 is the procedure identifier 225 ofthe equipment procedure 215 used with the equipment 160 that is beingaudited. The audit issues 243 may list issues arising from the auditthat require correction.

The mobile device 105 may scan the equipment reference code 205 toidentify the procedure data 210. The module device 105 may further scanan employee badge of the user to capture the user identifier 238. Themobile device 105 may also scan the procedure identifier 225 of theequipment 160.

The auditor may observe the user complying with the requirements of theequipment permit 270. In addition, the auditor may observe the userperforming the equipment procedure 215 associated with the equipmentreference code 205. The results of the audit are stored in the auditresult 236 as will be described hereafter.

FIGS. 2H and 2I are a schematic block diagrams illustrating embodimentsof site lists 262. In one embodiment, a first site list 262 a lists theequipment reference codes 205 of equipment 160 at the specified site.Alternatively, a second site list 262 b lists the procedure identifiers225 of equipment 160 at the specified site. The site list 262 may beused to determine which equipment permits 270 and/or equipmentprocedures 215 are synchronized from the procedure database 125 to themobile device 105. For example, only the equipment 160 group to aspecific site list 262 may be synchronized from the procedure database125 to the mobile device 105.

FIG. 2J is a schematic block diagram illustrating one embodiment of atutorial database 170. This tutorial database 170 is the tutorialdatabase 170 of FIG. 1. The tutorial database 170 stores a plurality ofequipment tutorials 295. Each of the equipment tutorials 295 may includeone or more of text instructions, hypertext instructions, audioinstructions, video instructions, image instructions, and the like forperforming one or more operations. An equipment tutorial 295 may bedirected to a specific equipment instance 160. Alternatively, a tutorial295 may be appropriate for multiple similar equipment instances 160.

FIG. 3A is a schematic block diagram illustrating one embodiment of thecomputer 300. The computer 300 may be the server 120 of FIG. 1.Alternatively, the computer 300 may be the mobile device 105 and/or theworkstation 135 of FIG. 1. The computer 300 includes a processor 305, amemory 310, and communication hardware 315. The memory 310 may be acomputer readable storage medium such as a semiconductor storage device,a hard disk drive, an optical drive, a holographic storage device, amicromechanical storage device, or combinations thereof. The memory 310may store program code. The processor 305 may execute the program code.The communication hardware 315 may communicate with other devices.

FIG. 3B is a schematic block diagram illustrating one embodiment of theprocedure apparatus 350. The apparatus 350 may be embodied in thecomputer 300. In one embodiment, the apparatus 350 is embodied in theserver 120, the mobile device 105, or combinations thereof. Theapparatus 350 includes a synchronization module 320 and a retrievalmodule 325. The synchronization module 320 and the retrieval module 325may be embodied in a computer readable storage medium such as the memory310 storing program code that is executed by the processor 305.

The synchronization module 320 may store a plurality of equipmentprocedures 215 and/or a plurality of equipment permits 270 in theprocedure database 125. Each equipment procedure 215 corresponds to anequipment instance 160 of a plurality of equipment instances 160 andeach equipment instance 160 corresponds to an equipment reference code205. In addition, the synchronization module 320 may synchronize one ormore of the plurality of equipment procedures 215 and/or equipmentpermits 270 to the mobile device 105.

The retrieval module 325 may receive the equipment reference code 205 atthe mobile device 105. In addition, the retrieval module 325 mayretrieve the equipment procedure 215 and/or equipment permit 270 indexedto the equipment reference code 205. In one embodiment, the retrievalmodule 325 retrieves the equipment procedure 215 and/or equipment permit270 from the mobile device 105. Additional functions of the apparatus350 are described hereafter.

FIG. 4A is a schematic flow chart diagram illustrating one embodiment ofa procedure provision method 500. The method 500 may provide anequipment permit 270 and/or an equipment procedure 215. The method 500may perform the functions of the system 100 and apparatus 350. In oneembodiment, the method 500 is performed by a computer readable storagemedium such as the memory 310 storing program code. The program code maybe executed by the processor 305 to perform the functions of the method500.

The method 500 starts, and in one embodiment the synchronization module320 stores 505 a plurality of equipment procedures 210 and/or aplurality of equipment permits 270 in a procedure database 125. Eachequipment procedure 215 may be indexed with a procedure identifier 225indexed to an equipment reference code 205. In addition, each equipmentpermit 270 may be indexed with an equipment reference code 205.

The synchronization module 320 may synchronize 510 an equipmentprocedure 215 and/or equipment permit 270 from the procedure database125 to the mobile device 105. In addition, the procedure data 210 and/orequipment data 211 associated with the equipment procedure 215 and/orequipment permit 270 may be synchronized from the procedure database 125to the mobile device 105. In one embodiment, all equipment procedures215 and/or equipment permits 270 are synchronized from the proceduredatabase 125 to the mobile device 105.

In an alternative embodiment, only equipment procedures 215 and/orequipment permits 270 with equipment reference codes 205 and/orprocedure identifiers 225 of a site list 262 are synchronized 510 to themobile device 105. The equipment procedures 215 may be grouped by sitewith a site list 262 for each site. A first site list 262 for a firstsite may include the equipment reference code 205 and/or procedureidentifier 225 corresponding to the equipment reference code 205 that isreceived by the mobile device 105.

The synchronization module 320 may synchronize 510 the equipmentprocedures 215 and/or equipment permits 270 grouped to the first site inresponse to the first equipment reference code 205 corresponding toequipment 160 of the first site. Alternatively, the synchronizationmodule 320 may synchronize 510 the equipment procedures 215 and/orequipment permits 270 of the first site list 262 to the mobile device105 if the first equipment reference code 205 and/or a procedureidentifier 225 corresponding to the first equipment reference code 205is included in the first site list 262. In one embodiment, the equipmentprocedures 215 and/or equipment permits 270 are synchronized 510 whenthe mobile device 105 is in communication with the network 115.

The retrieval module 325 receives 515 the equipment reference code 205.In one embodiment, the retrieval module 325 is embodied in the mobiledevice 105 and scans a QR code equipment reference code 205 affixed tothe equipment 160. Alternatively, the retrieval module 325 may receive515 the equipment reference code 205 by scanning a barcode, receivingthe equipment reference code 205 wirelessly, and/or by scanning humanreadable text. The retrieval module 325 may convert the scanned QR code,the scanned barcode, the human readable text, and/or the receivedequipment reference code 205 into a digital string embodying theequipment reference code 205.

The retrieval module 325 may retrieve 520 the equipment procedure 215and/or equipment permit 270 corresponding to the equipment referencecode 205 that is stored on the mobile device 105. In one embodiment, theretrieval module 325 uses the retrieval code 205 is an index to accessthe procedure identifiers 225 and/or equipment permit 270 for theequipment reference code 205. The retrieval module 325 may further usethe procedure identifiers 225 associated with the equipment referencecode 205 to retrieve the equipment procedures 215. If the equipmentprocedure 215 and/or equipment permit 270 corresponding to the equipmentreference code 205 are not stored on the mobile device 105, theretrieval module 325 may use the equipment reference code 205 and/orcorresponding procedure identifiers 225 to request the equipmentprocedure 215 and/or equipment permit 270 from the server 120 over thenetwork 115.

The equipment procedure 215 and/or equipment permit 270 may be displayed525 on the mobile device 105. Alternatively, the equipment procedure 215and/or equipment permit 270 may be communicated to a second device. Theuser may view the text, images, audio, and/or video of the equipmentprocedure 215 in order to understand how to operate and/or maintain theequipment 160.

In one embodiment, actions taken by the user are recorded 530 to theaudit report 230 and the method 500 ends. An auditor may record theactions on the mobile device 105 or the second device. Alternatively,the user may self-audit, and record the actions on the mobile device105. Recording 530 the actions taken by the user to the audit report 230is described in more detail in FIG. 4D.

FIG. 4B is a schematic flowchart diagram illustrating one embodiment ofan update method 502. The method 502 may update an equipment permit 270and/or an equipment procedure 215. The method 502 may perform thefunctions of the system 100 and apparatus 350. In one embodiment, themethod 502 is performed by a computer readable storage medium such asthe memory 310 storing program code. The program code may be executed bythe processor 305 to perform the functions of the method 502.

The method 502 starts, and in one embodiment, the retrieval module 325updates 550 an equipment procedure 215 and/or equipment permit 270. Theupdate may be entered by a user. The update may be entered from themobile device 105. Alternatively, the update may be entered from theworkstation 135. The synchronization module 320 may synchronize 555 theupdated equipment procedure 215 and/or updated equipment permit 270 tothe procedure database 125. In one embodiment, the updated equipmentprocedure 215 and/or updated equipment permit 270 may overwrite aprevious equipment procedure 215 and/or a previous equipment permit 270.Alternatively, the updated equipment procedure 215 and/or updatedequipment permit 270 may be appended to the procedure data 210 and/orequipment data 211. In addition, the updated equipment procedure 215and/or updated equipment permit 270 may be synchronize 555 from theprocedure database 125 to other mobile devices 105

In one embodiment, the server 120 may submit 560 the updated equipmentprocedure 215 and/or updated equipment permit 270 to a regulatoryauthority such as the Occupational Safety and Health Administration andthe method 502 ends. In one embodiment, the updated equipment procedure215 and/or updated equipment permit 270 are submitted as extended markuplanguage (XML) files.

FIG. 4C is a schematic flow chart diagram illustrating one embodiment ofa status provision method 600. The method 600 may provide and/or updatean equipment status 280. The method 600 may perform the functions of thesystem 100 and apparatus 350. In one embodiment, the method 600 isperformed by a computer readable storage medium such as the memory 310storing program code. The program code may be executed by the processor305 to perform the functions of the method 600.

The method 600 starts, and in one embodiment the synchronization module320 stores 605 a plurality of equipment statuses 280 in a proceduredatabase 125. Each equipment status 280 may be stored as part ofequipment data 211.

The synchronization module 320 may synchronize 610 an equipment status280 from the procedure database 125 to the mobile device 105. In oneembodiment, all equipment statuses 280 are synchronized 610 from theprocedure database 125 to the mobile device 105. In an alternativeembodiment, only equipment statuses 280 corresponding to equipmentreference codes 205 and/or procedure identifiers 225 of a site list 262are synchronized 610 to the mobile device 105. For example, theequipment statuses 280 of a first site list 262 that includes theequipment reference code 205 and/or procedure identifiers 225corresponding to the equipment reference code 205 may be synchronized610 to the mobile device 105. In one embodiment, the equipment statuses280 are synchronized 610 when the mobile device 105 is in communicationwith the network 115.

The retrieval module 325 receives 615 the equipment reference code 205.In one embodiment, the retrieval module 325 embodied in the mobiledevice 105 scans a QR code equipment reference code 205 affixed to theequipment 160. Alternatively, the retrieval module 325 may receive 615the equipment reference code 205 by scanning a barcode, receiving theequipment reference code 205 wirelessly, or by scanning human readabletext. The retrieval module 325 may convert the scanned QR code, thescanned barcode, the human readable text, and/or the received equipmentreference code 205 into a digital string of the equipment reference code205.

The retrieval module 325 may retrieve 620 the equipment status 280corresponding to the equipment reference code 205 that is stored on themobile device 105. In one embodiment, the retrieval module 325 uses theequipment reference code 205 as an index to access the equipment status280. If the equipment status 280 corresponding to the equipmentreference code 205 is not stored on the mobile device 105, the retrievalmodule 325 may use the equipment reference code 205 to request theequipment status 280 from the server 120 over the network 115. Theequipment status 280 may be displayed 623 on the mobile device 105.Alternatively, the equipment status 280 may be communicated to a seconddevice.

The retrieval module 325 may generate 625 an update of the equipmentstatus 280. The user may enter the update on the mobile device 105.Alternatively, the update may be generated 625 in response to the userindicating that a portion of the equipment procedure 215 is completed.In one embodiment, the update to the equipment status 280 may begenerated 625 from the audit report 230.

The synchronization module 320 may synchronize 630 the updated equipmentstatus 280 to the procedure database 125 and the method 600 ends. In oneembodiment, the updated equipment status 280 overwrites a previousequipment status 280 in the procedure database 125. Alternatively, theupdated equipment status 280 is appended to the equipment data 211 forthe equipment 160 in the procedure database 125.

FIG. 4D is a schematic flowchart diagram illustrating one embodiment ofan audit method 501. The method 501 may audit performance of anequipment procedure 215. The method 501 may perform the functions of thesystem 100 and apparatus 350. In one embodiment, the method 501 isperformed by a computer readable storage medium such as the memory 310storing program code. The program code may be executed by the processor305 to perform the functions of the method 501.

The method 501 starts, and in one embodiment the retrieval module 325records 530 a user following and/or performing an equipment procedure215. The retrieval module 325 may record 530 the following and/orperforming of the equipment procedure 215 to the audit result 236 of anaudit report 230. The retrieval module 325 may further record 530 theauditor performing the audit to the auditor data 232 and the useridentifier 238 of the user.

In one embodiment, the retrieval module 325 records 532 if the useremploys safety equipment specified by the equipment procedure 215 and/orequipment permit 270 to the audit result 236. For example, the equipmentprocedure 215 may specify the use of safety equipment such as eyeprotection. The retrieval module 325 may record 532 if the specifiedsafety equipment is used as part of the equipment procedure 215.

The retrieval module 325 may record 534 audit issues 243 for theequipment procedure 215 and/or equipment permit 270 to the audit results236. The audit issues 243 may include that the equipment 160 isincorrectly marked, that the equipment 160 lacks the required safetyequipment, that the equipment 160 is improperly ventilated, that theequipment 160 lacks a physical copy of the equipment procedure 215and/or equipment permit 270, that the steps of the equipment procedure215 and/or equipment permit 270 were incorrectly followed, that the userwas improperly trained, and the like.

In one embodiment, the retrieval module 325 records 536 an attestationfrom the auditor. The attestation may be an electronic signature, abiometric identifier, the signature image, or combinations thereof. Theretrieval module 325 may further record 538 an audit status 242 that mayindicate if the equipment procedure 215, equipment 160, user, orcombinations thereof passed the audit.

The synchronization module 320 may synchronize 539 the audit report 230to the audit database 165. The audit report 230 may be associated withthe procedure data 210 and/or the equipment data 211. In addition, thesynchronization module 320 may associate the audit report 230 with theuser data 260 of the user.

In one embodiment, the retrieval module 325 displays 540 an audit listof the audit statuses 242 for each equipment instance 160 and the method501 ends. The retrieval module 325 may also display 540 the audit status242 for one or more users. In addition, the audit list may include oneor more of the audit issues 243, the equipment statuses 280, and theprocedure statuses 217. The audit list may be displayed 540 for a sitelist 262. Alternatively, the retrieval module 325 displays 540 a summaryof the audit status for all users. The summary of the audit statuses 242may be used to show compliance with one or more regulations.

FIG. 4E is a schematic flow chart diagram illustrating one embodiment ofa tutorial provision method 650. The method 650 may provide equipmenttutorials 295 for an equipment procedure 215 and/or equipment permit270. The method 650 may perform the functions of the system 100 andapparatus 350. In one embodiment, the method 650 is performed by acomputer readable storage medium such as the memory 310 storing programcode. The program code may be executed by the processor 305 to performthe functions of the method 650.

The method 650 starts, and in one embodiment the synchronization module320 stores 655 a plurality of equipment tutorials 295 in the tutorialdatabase 170. Each equipment tutorial 295 may be indexed with anequipment reference code 205. Alternatively, each equipment tutorial 295may be indexed with a procedure identifier 225.

The synchronization module 320 may synchronize 660 an equipment tutorial295 from the procedure database 125 to the mobile device 105. In oneembodiment, all equipment tutorials 295 are synchronized from theprocedure database 125 to the mobile device 105. In an alternativeembodiment, only equipment tutorial 295 corresponding to equipmentreference codes 205 and/or procedure identifiers 225 of a site list 262are synchronized 510 to the mobile device 105. For example, theequipment tutorials 295 corresponding of a first site list 262 thatincludes the equipment reference code 205 and/or procedure identifiers225 corresponding to the equipment reference code 205 may besynchronized 660 to the mobile device 105. In one embodiment, thetutorials 295 are synchronized when the mobile device 105 is incommunication with the network 115.

The retrieval module 325 receives 665 the equipment reference code 205.In one embodiment, the retrieval module 325 embodied in the mobiledevice 105 scans a QR code equipment reference code 205 affixed to theequipment 160. Alternatively, the retrieval module 325 may receive 665the equipment reference code 205 by scanning a barcode, receiving theequipment reference code 205 wirelessly, or by scanning human readabletext. The retrieval module 325 may convert the scanned QR code, thescanned barcode, the human readable text, and/or the received equipmentreference code 205 into a digital string for the equipment referencecode 205.

The retrieval module 325 may retrieve 670 the equipment tutorial 295corresponding to the equipment reference code 205 that is stored on themobile device 105. In one embodiment, the retrieval module 325 uses theretrieval code 205 is an index to access the equipment tutorial 295. Ifthe equipment tutorial 295 corresponding to the equipment reference code205 is not stored on a mobile device 105, the retrieval module 325 mayuse the equipment reference code 205 to request the equipment tutorial295 from the server 120 over the network 115.

The equipment tutorial 295 may be displayed 675 on the mobile device 105and the method 650 ends. Alternatively, the equipment tutorial 295 maybe communicated to a second device. In one embodiment, a review of theequipment tutorial 295 by the user is recorded to the audit report 230.

The embodiments store equipment procedures 215 and/or equipment permits270 and synchronize the equipment procedures 215 and/or equipmentpermits 270 to the mobile device 105. The equipment procedures 215and/or equipment permits 270 may then be retrieved using an equipmentreference code 205 so that the latest equipment procedures 215 and/orequipment permits 270 are always accessible to users of the equipment160.

The embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. A method for providing procedures comprising:storing, by use of a processor, a plurality of equipment procedures in aprocedure database, wherein each equipment procedure corresponds to anequipment instance of a plurality of equipment instances and eachequipment instance corresponds to an equipment reference code;synchronizing the plurality of equipment procedures to a mobile device;receiving a first equipment reference code at the mobile device; andretrieving a first equipment procedure of the plurality of equipmentprocedures indexed to the first equipment reference code.
 2. The methodof claim 1, wherein the equipment procedure is an arc flash procedure.3. The method of claim 1, where the equipment procedure is a machineguarding procedure.
 4. The method of claim 1, wherein the equipmentprocedure is a maintenance procedure.
 5. The method of claim 1, whereinthe equipment procedure is an operating procedure.
 6. The method ofclaim 1, wherein the equipment procedure is an equipment hazardprocedure.
 7. The method of claim 1, the method further comprising:updating the first equipment procedure at the mobile device; andsynchronizing the updated first equipment procedure from the mobiledevice to the procedure database.
 8. The method of claim 7, the methodfurther comprising submitting the updated first equipment procedure to aregulatory authority.
 9. The method of claim 1, the method furthercomprising: recording whether a user follows the first equipmentprocedure to an audit report; and synchronizing the audit report to anaudit database with the audit report linked to the user in a userdatabase and linked to the first equipment procedure in the proceduredatabase.
 10. The method of claim 9, the method further comprising:recording audit issues for the first equipment procedure to the auditreport; recording an attestation from an auditor to the audit report;and recording an audit result to the audit report.
 11. The method ofclaim 9, the audit report comprising an auditor, the user, an audittime, an audit status, and the equipment reference code.
 12. The methodof claim 11, further comprising displaying the audit status for eachequipment instance and the audit status for the user.
 13. The method ofclaim 1, the method further comprising storing a plurality of equipmenttutorials in a tutorial database; synchronizing the plurality ofequipment tutorials to the mobile device; and retrieving a firsttutorial in response to the first equipment reference code.
 14. Themethod of claim 1, wherein the first equipment reference code is encodedas a Quick Response (QR) code.
 15. The method of claim 1, wherein thefirst equipment reference code is encoded as a barcode.
 16. The methodof claim 1, wherein the first equipment reference code is encoded as anidentification code of a Radio Frequency Identifier (RFID).
 17. Themethod of claim 1, wherein the equipment procedures are grouped by site.18. The method of claim 17, further comprising synchronizing theequipment procedures grouped to a first site in response to the firstequipment reference code corresponding to equipment of the first site.19. A program product comprising a non-transitory computer readablestorage medium that stores program code executable by a processor toperform: storing a plurality of equipment procedures in a proceduredatabase, wherein each equipment procedure corresponds to an equipmentinstance of a plurality of equipment instances and each equipmentinstance corresponds to an equipment reference code; synchronizing theplurality of equipment procedures to a mobile device; receiving a firstequipment reference code at the mobile device; and retrieving a firstequipment procedure of the plurality of equipment procedures indexed tothe first equipment reference code.
 20. An apparatus comprising: aprocessor; a non-transitory computer readable storage medium storingprogram code executable by the processor, the program code comprising: asynchronization module that stores a plurality of equipment proceduresin a procedure database, wherein each equipment procedure corresponds toan equipment instance of a plurality of equipment instances and eachequipment instance corresponds to an equipment reference code, and thatsynchronizes the plurality of equipment procedures to a mobile device;and a retrieval module that receives a first equipment reference code atthe mobile device and that retrieves a first equipment procedure of theplurality of equipment procedures indexed to the first equipmentreference code.